5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
- Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-8: Runtime Subroutine's and Predefined Processes

.WIDGET VIEW RUNTIME


This subroutine shows properties of the current --- WIDGET file.

Usage:

Description:

This subroutine shows properties of the current --- WIDGET file. There are no parameters.

This is useful for debugging your --- WIDGET file. You cannot simply run an input process with --- WIDGET as the PCF, since that input process will get it's own --- WIDGET file, and those will be the widgets you see, not the ones from your input process.

This routine will copy your existing --- WIDGET file to a memory file, and then show you the contents. You can invoke this subroutine in any event point that has widgets (ie, Pre-Display, Pre-Display/Verify, etc).

If you call this in the Pre-Display event point, you can make changes to the memory file and those changes will be copied back to your process. This can be a useful way of experimenting with different --- WIDGET fields. Note that if you use SCAN while doing this, some of the buttons from the SCAN display will get copied back to your image. This is annoying but harmless.

Application Design Manual                                         "Powered by Appx Software"

1213

©2006 By APPX Software, Inc. All Rights Reserved